xen init script: Do nothing if running for wrong Xen package
authorIan Jackson <ian.jackson@citrix.com>
Thu, 7 Feb 2019 15:56:49 +0000 (15:56 +0000)
committerHans van Kranenburg <hans@knorrie.org>
Wed, 13 Feb 2019 00:07:36 +0000 (01:07 +0100)
commitef242a700765a971a6afc12d25ee19944dd3a27a
treeb446e7bafc5b45bfadcfbb99610e4b80cd794bf6
parent30c9a3c54332f34c515143b261514a04e1e1d13c
xen init script: Do nothing if running for wrong Xen package

See the big comment.  We think that this is responsible for various
bugs and, particularly, reports of mysteriously missing xenconsoled.

For example, this bug would mean that after a Xen version upgrade,
autoremoval of an obsolete xen-utils-V package would stop the running
xenconsoled.  This is obviously awkward to track down, and could occur
many weeks or months after the upgrade.

Closes: #851654
Signed-off-by: Ian Jackson <ian.jackson@citrix.com>
Acked-by: Hans van Kranenburg <hans@knorrie.org>
debian/xen-utils-common.xen.init